Remote driving taxi system, mobility service management method, and remote driving taxi management device

ABSTRACT

A remote driving taxi system provides a mobility service using remote driving taxis that are driven by remote drivers. Management information indicates assignment states between the remote driving taxis and the remote drivers. The remote driving taxi system executes an assignment process based on the management information, in response to a request from a user. Specifically, the remote driving taxi system selects one of unassigned taxis to each of which the remote driver has not been assigned, as a first remote driving taxi that provides the service to the user. Further, the remote driving taxi system selects one of remote drivers each of which has not been assigned to the remote driving taxi, as a first remote driver that provides the service to the user. Then, the remote driving taxi system assigns the first remote driver to the first remote driving taxi.

CROSS-REFERENCE TO RELATED APPLICATION

This application claims priority to Japanese Patent Application No. 2021-120681 filed on Jul. 21, 2021, incorporated herein by reference in its entirety.

BACKGROUND 1. Technical Field

The present disclosure relates to a mobility service using remote driving taxis that are driven by remote drivers.

2. Description of Related Art

Japanese Unexamined Patent Application Publication No. 2004-295360 discloses a vehicle remote driving device that drives a vehicle by remote operation.

SUMMARY

In the case of an existing taxi service, each taxi driver drives one taxi in a limited region. That is, the taxi driver is bound by the location and the vehicle. This causes loss of work opportunity and decrease in operational efficiency.

An object of the present disclosure is to provide a new mobility service.

A first aspect relates to a remote driving taxi system that provides a mobility service, the mobility service using remote driving taxis that are driven by remote drivers. The remote driving taxi system includes: a single or a plurality of processors; and a single or a plurality of storage devices configured to store management information including assignment states between the remote driving taxis and the remote drivers. The single or the plurality of processors executes an assignment process based on the management information, in response to a request from a user. In the assignment process, the single or the plurality of processors selects one of unassigned taxis as a first remote driving taxi that provides the mobility service to the user, each of the unassigned taxis being the remote driving taxi to which the remote driver has not been assigned, selects one of unassigned drivers as a first remote driver that provides the mobility service to the user, each of the unassigned drivers being the remote driver that has not been assigned to the remote driving taxi, and assigns the first remote driver to the first remote taxi.

A second aspect relates to a mobility service management method for managing a mobility service, the mobility service using remote driving taxis that are driven by remote drivers. The mobility service management method includes: a process of acquiring management information including assignment states between the remote driving taxis and the remote drivers; and a process of executing an assignment process based on the management information, in response to a request from a user. The assignment process includes: a process of selecting one of unassigned taxis as a first remote driving taxi that provides the mobility service to the user, each of the unassigned taxis being the remote driving taxi to which the remote driver has not been assigned; a process of selecting one of unassigned drivers as a first remote driver that provides the mobility service to the user, each of the unassigned drivers being the remote driver that has not been assigned to the remote driving taxi; and a process of assigning the first remote driver to the first remote taxi.

A third aspect relates to a remote driving taxi management device that manages a mobility service, the mobility service using remote driving taxis that are driven by remote drivers. The remote driving taxi management device includes: a single or a plurality of processors; and a single or a plurality of storage devices configured to store management information including assignment states between the remote driving taxis and the remote drivers. The single or the plurality of processors executes an assignment process based on the management information, in response to a request from a user. In the assignment process, the single or the plurality of processors selects one of unassigned taxis as a first remote driving taxi that provides the mobility service to the user, each of the unassigned taxis being the remote driving taxi to which the remote driver has not been assigned, selects one of unassigned drivers as a first remote driver that provides the mobility service to the user, each of the unassigned drivers being the remote driver that has not been assigned to the remote driving taxi, and assigns the first remote driver to the first remote taxi.

The resent disclosure provides a new mobility service using remote driving taxis that are driven by remote drivers. The remote drivers are not bounded by either vehicles or locations. Consequently, the work opportunity is increased, and the operational efficiency is enhanced.

BRIEF DESCRIPTION OF THE DRAWINGS

Features, advantages, and technical and industrial significance of exemplary embodiments of the disclosure will be described below with reference to the accompanying drawings, in which like signs denote like elements, and wherein:

FIG. 1 is a conceptual diagram for describing an overview of a remote driving taxi service according to an embodiment of the present disclosure;

FIG. 2 is a conceptual diagram showing an exemplary configuration of the remote driving taxi system according to the embodiment of the present disclosure;

FIG. 3 is a block diagram for describing an assignment process according to the embodiment of the present disclosure;

FIG. 4 is a conceptual diagram for describing an example of vehicle management information according to the embodiment of the present disclosure;

FIG. 5 is a conceptual diagram for describing an example of driver management information according to the embodiment of the present disclosure;

FIG. 6 is a conceptual diagram for describing an example of assignment management information according to the embodiment of the present disclosure;

FIG. 7 is a flowchart showing an example of the assignment process according to the embodiment of the present disclosure;

FIG. 8 is a flowchart showing another example of the assignment process according to the embodiment of the present disclosure;

FIG. 9 is a conceptual diagram for describing an example of a display lamp control according to the embodiment of the present disclosure;

FIG. 10 is a conceptual diagram for describing a traveling restriction process according to the embodiment of the present disclosure;

FIG. 11 is a block diagram showing an exemplary configuration of a remote driving taxi according to the embodiment of the present disclosure;

FIG. 12 is a block diagram showing an exemplary configuration of a remote driver terminal according to the embodiment of the present disclosure; and

FIG. 13 is a block diagram showing an exemplary configuration of a remote driving taxi management device according to the embodiment of the present disclosure.

DETAILED DESCRIPTION OF EMBODIMENTS

An embodiment of the present disclosure will be described with reference to the accompanying drawings.

1. Remote Driving Taxi Service

FIG. 1 is a conceptual diagram for describing an overview of a remote driving taxi service. The remote driving taxi service is a mobility service that uses remote driving taxis 100. The remote driving taxis 100 are vehicles that allow remote driving, and are remotely driven (remotely operated) by remote drivers 1. Typically, no driver is in the remote driving taxi 100. The remote driver 1 is flexibly assigned to the remote driving taxi 100, and drives the assigned remote driving taxi 100. A user in the remote driving taxi service can move to a destination by using the remote driving taxi 100 that is driven by the remote driver 1.

A characteristic of the remote driving taxi service is that the remote driver 1 is not bound by either vehicles or locations. For example, the remote driver 1 can work by driving a remote driving taxi 100-1 in a first region, and soon, can work by driving another remote driving taxi 100-2 in a second region. The first region and the second region may be distant from each other. For example, the first region may be Hokkaido, and the second region may be Kyushu. The remote driver 1 can work by driving an arbitrary remote driving taxi 100 in an arbitrary region.

As a comparison, an existing taxi service will be discussed. In the case of the existing taxi service, the taxi driver drives one taxi in a limited region. That is, the taxi driver is bound by the location and the vehicle. For example, a taxi driver that works in a region where the number of users is small waits for a customer with doing nothing for a long time, naturally. When the number of users in the region is small, the taxi driver cannot work even if the work motivation is high. This means a loss of work opportunity. As another example, in the case where the taxi driver carries a customer over a long distance, the taxi driver needs to return to a home place from a faraway place after the customer gets off the taxi at the faraway place. When the taxi driver returns to the home place from the faraway place, the taxi driver cannot always carry a customer luckily. When the taxi driver must drive the taxi in an empty state over a long distance, the operational efficiency decreases.

On the other hand, in the case of the remote driving taxi service, the remote driver 1 is not bound by either the vehicle or the location, and therefore the problem in the case of the existing taxi service does not occur. For example, the remote driver 1 does not need to continue to wait for a customer in a region where the number of users is small, and can work one after another in response to requests from users in various regions. In the region where the number of users is small, by disposing only the remote driving taxi 100, it is possible to provide the remote driving taxi service, even if there is actually no driver. As another example, even in the case where the remote driver 1 carries a passenger to a destination that is distant from a departure place, the remote driver 1 does not need to return to the departure place while driving the used remote driving taxi 100. If the remote driver 1 wants to continuously work in another region, the remote driver 1 only needs to park the previously used remote driving taxi 100 at a taxi parking area near the previous destination. The remote driving taxi 100 can be used by another remote driver 1.

In this way, the remote driving taxi service makes remarkable effects such as increase in work opportunity and enhancement in operational efficiency. A remote driving taxi system for realizing the remote driving taxi service will be described below.

2. Overview of Remote Driving Taxi System

FIG. 2 is a conceptual diagram showing an exemplary configuration of the remote driving taxi system 10 according to the embodiment. The remote driving taxi system 10 provides the remote driving taxi service. The remote driving taxi system 10 includes one or more remote driving taxis 100, one or more remote driver terminals 200, and a remote driving taxi management device 300.

The remote driving taxi 100 is a vehicle that allows remote driving. The remote driving taxi 100 is equipped with various sensors, and can acquire information such as a current position, a vehicle state, and a peripheral situation. Further, the remote driving taxi 100 can wirelessly communicate with the remote driving taxi management device 300.

The remote driver terminal 200 is a device that is used by the remote driver 1 for remotely driving (remotely operating) the remote driving taxi 100. The remote driver terminal 200 includes a display device. Further, the remote driver terminal 200 includes a remote operation member that is operated when the remote driver 1 remotely drives the remote driving taxi 100. Further, the remote driver terminal 200 can communicate with the remote driving taxi management device 300.

The remote driving taxi management device 300 manages the remote driving taxi service. For example, the remote driving taxi management device 300 manages the remote driver 1 and the remote driving taxi 100. Further, the remote driving taxi management device 300 can communicate with each remote driving taxi 100 and each remote driver terminal 200. The remote driving taxi management device 300 may be included in a mobility service management system that manages the whole of the mobility service. Typically, the remote driving taxi management device 300 is a management server on the cloud. The management server may be constituted by a plurality of servers that performs distributed processing.

The remote driving taxi system 10 may further include a user terminal 400. Examples of the user terminal 400 include a smartphone and a PC. The user terminal 400 executes an application for using the remote driving taxi service. Further, the user terminal 400 can communicate with the remote driving taxi management device 300.

A basic flow of the remote driving taxi service is shown as follows.

First, the remote driving taxi management device 300 executes an “assignment process” of assigning the remote driver 1 to the remote driving taxi 100. Details of the assignment process will be described later.

The remote driver 1 remotely drives the assigned remote driving taxi 100. Specifically, the remote driving taxi 100 acquires the information such as the current position, the vehicle state, and the peripheral situation, using various sensors, and sends vehicle information VCL including the acquired information, to the remote driving taxi management device 300. The remote driving taxi management device 300 transfers the received vehicle information VCL to the remote driver terminal 200 that is used by the remote driver 1. The remote driver terminal 200 displays the received vehicle information VCL and map information on the display device. The remote driver 1 operates the remote operation member of the remote driver terminal 200, while referring to the map information and vehicle information VCL displayed on the display device. The remote driver terminal 200 sends operation information OPE indicating an operation amount of the remote operation member, to the remote driving taxi management device 300. The remote driving taxi management device 300 transfers the received operation information OPE to the remote driving taxi 100. The remote driving taxi 100 performs a vehicle traveling control in accordance with the received operation information OPE.

The remote driver 1 drives the assigned remote driving taxi 100, and picks up the user. Then, the remote driver 1 drives the remote driving taxi 100 to a destination designated by the user. When the remote driver 1 arrives at the destination, the remote driver 1 drops off the user.

3. Assignment Process

FIG. 3 is a block diagram for describing the assignment process by the remote driving taxi management device 300 according to the embodiment. In the assignment process, the remote driving taxi management device 300 flexibly assigns the remote driver 1 to the remote driving taxi 100.

3-1. Management Information

The remote driving taxi management device 300 holds management information 500, and executes the assignment process based on the management information 500. The management information 500 includes vehicle management information 510, driver management information 520, and assignment management information 530.

3-1-1. Vehicle Management Information

FIG. 4 is a conceptual diagram for describing an example of the vehicle management information 510. The vehicle management information 510 is information for managing the remote driving taxi 100, and includes an entry for each remote driving taxi 100. For example, each entry includes a vehicle ID, a vehicle type, a use state, a driver in charge, a current position, a destination, a traveling state, and the like.

The vehicle ID is identification information about the remote driving taxi 100. The vehicle ID may include number plate information (vehicle registration number) about the remote driving taxi 100.

The vehicle type is the type of the remote driving taxi 100. Examples of the vehicle type include a large size, a middle size, and a small size. The vehicle type may include a manufacturer and a vehicle name.

The use state is the current use state of the remote driving taxi 100. Examples of the use state include an in-service state (in practice), a picking-up state, and an empty state (available). Further, the use state indicates also whether one of the remote drivers 1 has been assigned to the remote driving taxi 100.

The driver in charge indicates a driver ID of the remote driver 1 that has been assigned to the remote driving taxi 100.

The current position is the current position of the remote driving taxi 100. The current position is included in the vehicle information VCL that is sent from the remote driving taxi 100.

The destination is the destination of the remote driving taxi 100. For example, the destination is included in a service request REQ_U (described later) from the user. As other examples, the destination may be designated by the user that has got in the remote driving taxi 100, or may be sent from the remote driving taxi 100.

The traveling state is the traveling state of the remote driving taxi 100. The traveling state is included in the vehicle information VCL that is sent from the remote driving taxi 100.

3-1-2. Driver Management Information

FIG. 5 is a conceptual diagram for describing an example of the driver management information 520. The driver management information 520 is information for managing the remote driver 1, and includes an entry for each remote driver 1. For example, each entry includes a driver ID, a driver state, an assignment vehicle, a driver property, and the like.

The driver ID is identification information about the remote driver 1. The driver ID may include the name of the remote driver 1.

The driver state is the current state of the remote driver 1. Examples of the driver state include an in-service state (passenger transporting state), a picking-up state, an open state (available). Further, the driver state indicates also whether the remote driver 1 has been assigned to one of the remote driving taxis 100.

The assignment vehicle indicates the vehicle ID of the remote driving taxi 100 to which the remote driver 1 is assigned.

The driver property indicates a taste and characteristic of the remote driver 1. For example, the driver property includes a desired area, a desired vehicle type, a rank, an obtained point, and the like.

The desired area is a region that is desired by the remote driver 1. The desired area is previously designated by the remote driver 1. For example, the remote driver 1 designates an area where the remote driver 1 is familiar with roads, as the desired area.

The desired vehicle type is the vehicle type of the remote driving taxi 100 that is desired by the remote driver 1. The desired vehicle type is previously designated by the remote driver 1.

The rank is the current rank of the remote driver 1. For example, the remote driver 1 is classified as one of ranks of five-star to no-star. As another example, the remote driver 1 may be classified as one of ranks of “excellent (SS)”, “good (S)”, “general (A)” and “beginner (B)”. The rank of the remote driver 1 may reflect the evaluation (rating) by the user. The rank may be reflected by taxi usage fee. The rank may be reflected by the pay to the remote driver 1.

The obtained point is the number of points that the remote driver 1 has obtained until the current time. For example, the point increases depending on the number of times of the carrying of the passenger. As another example, the point increases depending on a traveling distance by which the remote driver 1 has traveled while carrying the passenger. The increase in the point may raise the rank.

The rank and the point are expected to cause the enhancement in service quality and the increase in work motivation. Further, the rank and the point generate a game element in the remote driving taxi service. As a result, the remote driver 1 can enjoy working. This also contributes to the increase in work motivation and the enhancement in service quality.

3-1-3. Assignment Management Information

FIG. 6 is a conceptual diagram for describing an example of the assignment management information 530. The assignment management information 530 is information for managing the assignment state between the remote driver 1 and the remote driving taxi 100. For example, the assignment management information 530 includes an assignment relation information 531, an unassigned taxi list 532, and an unassigned driver list 533.

The assignment relation information 531 indicates a correspondence relation between the remote driving taxi 100 and the remote driver 1 that are assigned. For example, the assignment relation information 531 indicates a correspondence relation between the vehicle ID of the remote driving taxi 100 and the driver ID of the remote driver 1 assigned to the remote driving taxi 100. In the case where a target user to which the remote driver 1 (the remote driving taxi 100) provides the service has already been decided, the assignment relation information 531 indicates also a correspondence relation with the target user.

Hereinafter, a remote driving taxi 100 to which the remote driver 1 has not yet been assigned is referred to as an “unassigned taxi 100N”. The unassigned taxi list 532 is a list of unassigned taxis 100N, and indicates the vehicle IDs of the unassigned taxis 100N. The unassigned taxi list 532 may include a waiting list having a cue format. The waiting list indicates a priority order of the unassigned taxis 100N relevant to the assignment process.

Hereinafter, a remote driver 1 that has not yet been assigned to the remote driving taxi 100 is referred to as an “unassigned driver 1N”. The unassigned driver list 533 is a list of unassigned drivers 1N, and indicates the driver IDs of the unassigned drivers 1N. The unassigned driver list 533 may include a waiting list having a cue format. The waiting list indicates a priority order of the unassigned drivers 1N relevant to the assignment process.

3-2. Assignment Process Responding to Request from Driver

FIG. 7 is a flowchart showing an example of the assignment process by the remote driving taxi management device 300 according to the embodiment. In the example, it is assumed that the remote driver 1 waits for a customer in front of a station or looks for a customer in a city.

In step S310, the unassigned driver 1N operates the remote driver terminal 200, to send an assignment request REQ_D to the remote driving taxi management device 300. For convenience, the unassigned driver 1N that sends the assignment request REQ_D is referred to as a “request driver 1R”. The remote driving taxi management device 300 receives the assignment request REQ_D from the remote driver terminal 200.

In step S320, the remote driving taxi management device 300 executes the assignment process in response to the assignment request REQ_D. Specifically, the remote driving taxi management device 300 selects one of unassigned taxis 100N based on the management information 500. The unassigned taxis 100N are obtained from the unassigned taxi list 532. For convenience, the selected unassigned taxi 100N is referred to as a “first remote driving taxi 100S”. The remote driving taxi management device 300 assigns the request driver 1R to the first remote driving taxi 100S.

In the case where the unassigned taxi list 532 includes the waiting list, the remote driving taxi management device 300 may select the first remote driving taxi 100S in accordance with the priority order indicated in the waiting list.

The remote driving taxi management device 300 may select the first remote driving taxi 100S based on the driver property information included in the driver management information 520. The driver property information includes the desired area and desired vehicle type for the request driver 1R. For example, the remote driving taxi management device 300 may select the unassigned taxi 100N that exists in the desired area for the request driver 1R, as the first remote driving taxi 100S. As another example, the remote driving taxi management device 300 may select the unassigned taxi 100N that meets the desired vehicle type for the request driver 1R, as the first remote driving taxi 100S. The current position and vehicle type of the unassigned taxi 100N are obtained from the vehicle management information 510.

In step S330, the remote driving taxi management device 300 updates the management information 500 based on a result of the assignment process. Particularly, the remote driving taxi management device 300 updates the management information 500 related to the request driver 1R and the first remote driving taxi 100S.

In step S340, the remote driving taxi management device 300 sends an assignment notice ASN to the remote driver terminal 200. The assignment notice ASN indicates the completion of the assignment process, the assigned first remote driving taxi 100S, and the like. The remote driver terminal 200 presents the assignment notice ASN to the request driver 1R.

In the case where there is no unassigned taxi 100N that can be assigned, the remote driving taxi management device 300 may register the request driver 1R in the unassigned driver list 533 (waiting list) as “assignment waiting”.

After the completion of the assignment process, the remote driver 1 can drive the assigned remote driving taxi 100. For example, the remote driver 1 can wait for a customer in front of a station. As another example, the remote driver 1 can look for a customer in a city.

3-3. Assignment Process Responding to Request from User

FIG. 8 is a flowchart showing another example of the assignment process by the remote driving taxi management device 300 according to the embodiment.

In step S350, the remote driving taxi management device 300 receives a service request REQ_U from the user.

For example, the user executes an application on the user terminal 400, and inputs the service request REQ_U. The service request REQ_U includes a desired getting-in position that is designated by the user. Alternatively, the current position of the user terminal 400 may be regarded as the desired getting-in position. The service request REQ_U may include a desired getting-in time that is designated by the user. The service request REQ_U may include a destination that is designated by the user. The service request REQ_U may include a vehicle type of the remote driving taxi 100 that is desired by the user. The service request REQ_U may include a rank of the remote driver 1 that is desired by the user. The service request REQ_U may include the driver ID of the remote driver 1 that is designated by the user. The application on the user terminal 400 sends the service request REQ_U to the remote driving taxi management device 300.

As another example, an outside-vehicle human machine interface (HMI) may be attached to a side surface of the remote driving taxi 100. In this case, the user can convey an intention to use the remote driving taxi 100, by operating the outside-vehicle HMI. For example, the user presses a “use start button” that is displayed on the outside-vehicle HMI. Further, the user may designate a desired rank of the remote driver 1, by operating the outside-vehicle HMI. The remote driving taxi 100 sends the service request REQ_U to the remote driving taxi management device 300, in response to the operation of the outside-vehicle HMI by the user. The service request REQ_U includes the vehicle ID of the remote driving taxi 100 and the current position. The current position of the remote driving taxi 100 corresponds to the desired getting-in position.

In step S360, the remote driving taxi management device 300 executes the assignment process in response to the service request REQ_U. Specifically, the remote driving taxi management device 300 selects the unassigned taxi 100N and unassigned driver 1N that provide the service to the user, based on the management information 500. That is, the remote driving taxi management device 300 selects one unassigned taxi 100N and one unassigned driver 1N, and assigns the unassigned taxi 100N and the unassigned driver 1N to the user. For convenience, the selected unassigned taxi 100N is referred to as a “first remote driving taxi 100S”. Further, for convenience, the selected unassigned driver 1N is referred to a “first remote driver 1S”. The remote driving taxi management device 300 assigns the first remote driver 1S to the first remote driving taxi 100S.

For example, in the case where the user desires to use a certain remote driving taxi 100 and operates the outside-vehicle HMI of the certain remote driving taxi 100, the remote driving taxi management device 300 selects the certain remote driving taxi 100 as the first remote driving taxi 100S.

The case where the service request REQ_U is sent from the user terminal 400 is shown as follows. The service request REQ_U includes the desired getting-in position. The vehicle management information 510 includes the current position of each remote driving taxi 100. The unassigned taxi 100N is obtained from the unassigned taxi list 532. The remote driving taxi management device 300 selects the unassigned taxi 100N near the desired getting-in position, as the first remote driving taxi 100S, based on the management information 500. More specifically, the remote driving taxi management device 300 selects the first remote driving taxi 100S from unassigned taxis 100N that exist within a predetermined range from the desired getting-in position.

In the case where the unassigned taxi list 532 includes the waiting list, the remote driving taxi management device 300 may select the first remote driving taxi 100S in accordance with the priority order indicated in the waiting list.

In the case where the service request REQ_U includes the desired vehicle type for the user, the remote driving taxi management device 300 may select the unassigned taxi 100N that meets the desired vehicle type for the user, as the first remote driving taxi 100S.

The first remote driver 1S will be described below. The remote driving taxi management device 300 selects the first remote driver 1S from the unassigned drivers 1N. The unassigned drivers 1N are obtained from the unassigned driver list 533. In the case where the unassigned driver list 533 includes the waiting list, the remote driving taxi management device 300 may select the first remote driver 1S in accordance with the priority order indicated in the waiting list.

The remote driving taxi management device 300 may select the first remote driver 1S based on the driver property information included in the driver management information 520.

For example, the driver property information includes the desired area for each remote driver 1. The current position of the first remote driving taxi 100S is obtained from the vehicle management information 510. The remote driving taxi management device 300 may select the unassigned driver 1N for which the desired area contains the current position of the first remote driving taxi 100S, as the first remote driver 1S.

As another example, the driver property information includes the desired vehicle type for each remote driver 1. The vehicle type of the first remote driving taxi 100S is obtained from the vehicle management information 510. The remote driving taxi management device 300 may select the unassigned driver 1N for which the desired vehicle type coincides with the vehicle type of the first remote driving taxi 100S, as the first remote driver 1S.

Furthermore, as another example, the driver property information includes the rank of each remote driver 1. The service request REQ_U from the user may include a rank of the remote driver 1 that is desired by the user. The remote driving taxi management device 300 may select the unassigned driver 1N for which the rank is equal to or higher than the rank that is desired by the user, as the first remote driver 1S.

Furthermore, as another example, the user may designate a desired remote driver 1. In that case, the service request REQ_U includes the driver ID of the remote driver 1 designated by the user. The remote driving taxi management device 300 selects the remote driver 1 designated by the user, as the first remote driver 1S.

The remote driving taxi management device 300 may deliver the service request REQ_U to the remote driver terminals 200 of all unassigned drivers 1N that meet the condition. In the case where the unassigned driver 1N hopes to provide the service to the user, the unassigned driver 1N returns an acceptance intention to the remote driving taxi management device 300. The remote driving taxi management device 300 may select the unassigned driver IN that returned the acceptance intention earliest, as the first remote driver 1S.

The remote driving taxi management device 300 assigns the selected first remote driver 1S to the selected first remote driving taxi 100S.

In step S370, the remote driving taxi management device 300 updates the management information 500 based on a result of assignment process. Particularly, the remote driving taxi management device 300 updates the management information 500 related to the first remote driver 1S and the first remote driving taxi 100S.

In step S380, the remote driving taxi management device 300 sends the assignment notice ASN to the remote driver terminal 200 of the first remote driver 1S. The assignment notice ASN indicates the completion of the assignment process, the assigned first remote driving taxi 100S, the desired getting-in position, the desired getting-in time, the destination, and the like. The remote driver terminal 200 presents the assignment notice ASN to the request driver 1R.

Further, the remote driving taxi management device 300 sends service information INF to the user terminal 400. The service information INF includes information relevant to the first remote driver 1S and first remote driving taxi 100S that provide the service to the user. For example, the service information INF may include the vehicle type and number plate information about the first remote driving taxi 100S. The service information INF may include the name and rank of the first remote driver 1 s.

After the completion of the assignment process, the first remote driver 1S can drive the assigned first remote driving taxi 100S. The first remote driver 1S moves the first remote driving taxi 100S to the desired getting-in position, and picks up the user.

4. Display Lamp Control

Whether the remote driving taxi 100 is currently available is decided depending on the current use state of the remote driving taxi 100. For example, in the case where the use state is the “in-service state” or the “picking-up state”, the remote driving taxi 100 is unavailable. On the other hand, in the case where the use state is the “empty state”, the remote driving taxi 100 is available.

Since no driver is in the remote driving taxi 100, it can be difficult for the user to determine whether the remote driving taxi 100 is available. Hence, the remote driving taxi system 10 according to the embodiment executes a “display lamp control” for appropriately giving notice of whether the remote driving taxi 100 is available.

FIG. 9 is a conceptual diagram for describing an example of the display lamp control according to the embodiment. The remote driving taxi 100 includes a display lamp 140 that indicates whether the remote driving taxi 100 is currently available. Typically, the display lamp 140 is attached to a roof of the remote driving taxi 100. In the case where the display lamp 140 is in an on-state, the display lamp 140 means that the remote driving taxi 100 is currently available. On the other hand, in the case where the display lamp 140 is an off-state, the display lamp 140 means that the remote driving taxi 100 is currently unavailable.

As described above, the vehicle management information 510 indicates the use state of each remote driving taxi 100. Further, the assignment management information 530 indicates the assignment state between the remote driver 1 and the remote driving taxi 100. The remote driving taxi system 10 according to the embodiment executes the display lamp control based on the management information 500.

First, the remote driving taxi 100 to which the remote driver 1 has already been assigned will be discussed. The remote driving taxi system 10 automatically puts on the display lamp 140 of the remote driving taxi 100 that is currently available, and automatically puts off the display lamp 140 of the remote driving taxi 100 that is currently unavailable. More specifically, the remote driving taxi management device 300 recognizes the use state of the remote driving taxi 100 to which the remote driver 1 has already assigned, based on the management information 500. Then, the remote driving taxi management device 300 sends instruction information INS for giving an instruction to put on or put off the display lamp 140, to the remote driving taxi 100, depending on the use state. The remote driving taxi 100 automatically puts on or puts off its own display lamp 140, in accordance with the received instruction information INS. In this way, the remote driving taxi system 10 (the remote driving taxi management device 300) automatically controls the lighting state of the display lamp 140 of the remote driving taxi 100.

Next, the unassigned taxi 100N to which the remote driver 1 has not yet assigned will be discussed. The unassigned taxi 100N can be recognized based on the unassigned taxi list 532.

In a first example, the remote driving taxi system 10 automatically puts off the display lamp 140 of the unassigned taxi 100N.

In a second example, “the number of unassigned drivers 1N” is considered. The unassigned driver 1N can be recognized based on the unassigned driver list 533. When there is an unassigned driver 1N, it is possible to immediately assign the unassigned driver 1N to the unassigned taxi 100N, in response to the service request REQ_U from the user. That is, when there is an unassigned driver 1N, it is possible to immediately put the unassigned taxi 100N into an available state, without keeping the user waiting. From the above standpoint, the remote driving taxi system 10 selects the unassigned taxi 100N that puts on the display lamp 140, depending on the number of unassigned drivers 1N. For example, the remote driving taxi system 10 selects unassigned taxis 100N to a number equal to or smaller than the number of unassigned drivers 1N. The remote driving taxi system 10 may select unassigned taxis 100N to the same number as the number of unassigned drivers 1N. Then, the remote driving taxi system 10 automatically puts on the display lamps 140 of the selected unassigned taxis 100N, and automatically puts off the display lamps 140 of the other unassigned taxis 100N. By appropriately putting on the display lamp 140 of the unassigned taxi 100N, it is possible to increase options for the user.

In a third example, the unassigned taxi list 532 includes the waiting list indicating the priority order of the unassigned taxi 100N relevant to the assignment process. It is expected that the remote driver 1 can be assigned to the unassigned taxi 100N having a high order in the waiting list immediately or in a short waiting time. From the above standpoint, the remote driving taxi system 10 selects unassigned taxis 100N from the top to a predetermined order in the waiting list. Then, the remote driving taxi system 10 automatically puts on the display lamps 140 of the selected unassigned taxis 100N, and automatically puts off the display lamps 140 of the other unassigned taxis 100N. By appropriately putting on the display lamp 140 of the unassigned taxi 100N, it is possible to increase options for the user.

In each of the above first to third examples, the remote driving taxi management device 300 can decide whether to put on the display lamp 140 for each unassigned taxi 100N, based on the management information 500. Then, the remote driving taxi management device 300 sends the instruction information INS for giving the instruction to put on or put off the display lamp 140, to the unassigned taxi 100N. The unassigned taxi 100N automatically puts on or puts off its own display lamp 140, in accordance with the received instruction information INS. In this way, the remote driving taxi system 10 (the remote driving taxi management device 300) automatically controls the lighting state of the display lamp 140 of the remote driving taxi 100.

As a modification, in the case where the display lamp 140 is put on, the “showing way” may be changed depending on whether the remote driver 1 has already been assigned to the remote driving taxi 100. For example, in the case where the remote driver 1 has been assigned, the display lamp 140 may be put on more brightly than in the case where the remote driver 1 has not been assigned.

As described above, the notice of whether the remote driving taxi 100 is available is appropriately given by the putting-on/putting-off of the display lamp 140 of the remote driving taxi 100. Thereby, the user can easily recognize whether the remote driving taxi 100 is available.

5. Traveling Restriction Process

FIG. 10 is a conceptual diagram for describing a “traveling restriction process” according to the embodiment. The remote driving taxi system 10 restricts the traveling of the designated remote driving taxi 100, as necessary. For example, as a traveling restriction, the vehicle speed upper limit is set to a value lower than a default value. As another example, the traveling restriction includes an emergency stop. Furthermore, as another example, the traveling restriction includes an evacuation to a safe position such as a road shoulder.

For example, from the remote driving taxi 100 that is being driven by the remote driver 1, the remote driving taxi management device 300 acquires the vehicle information VCL including the traveling state of the remote driving taxi 100. The remote driving taxi management device 300 monitors the traveling state of the remote driving taxi 100 based on the vehicle information VCL, and determines whether there is abnormal traveling. Examples of the abnormal traveling include an oversight of a traffic sign, a violation of a traffic regulation, and erratic driving. For the violation of the traffic regulation, a certain permissible range may be set because there can be an unavoidable circumstance. In the case where the abnormal traveling is detected, the remote driving taxi management device 300 sends the instruction information INS for giving an instruction of the traveling restriction, to the remote driving taxi 100 that is performing the abnormal traveling. The remote driving taxi 100 receives the instruction information INS, and performs the traveling restriction in accordance with the instruction information INS.

As another example, the remote driving taxi 100 that is being driven by the remote driver 1 may acquire the vehicle information VCL, and may determine whether there is the abnormal driving of the remote driving taxi 100 itself, based on the vehicle information VCL. In the case where the abnormal traveling is detected, the remote driving taxi 100 performs the traveling restriction.

Furthermore, as another example, the remote driver terminal 200 may include a driver monitor that detects biological information (heart rate, pulse, eye movement, and the like) about the remote driver 1. The remote driver terminal 200 determines whether there is an abnormality of the remote driver 1, based on a detection result by the driver monitor. Examples of the abnormality of the remote driver 1 include a catnap and a sudden illness. In the case where the abnormality of the remote driver 1 is detected, the remote driver terminal 200 gives notice of the occurrence of the driver abnormality, to the remote driving taxi management device 300. The remote driving taxi management device 300 sends the instruction information INS for giving the instruction of the traveling restriction, to the remote driving taxi 100 that is being driven by the remote driver 1 in which the abnormality has occurred. The remote driving taxi 100 receives the instruction information INS, and performs the traveling restriction in accordance with the instruction information INS.

Furthermore, as another example, the remote driving taxi management device 300 may receive the biological information detected by the driver monitor, from the remote driver terminal 200. In this case, the remote driving taxi management device 300 determines whether there is the abnormality of the remote driver 1.

In this way, the remote driving taxi system 10 (the remote driving taxi management device 300, the remote driving taxi 100) controls the remote driving taxi 100 such that the remote driving taxi 100 performs the traveling restriction, as necessary. By the traveling restriction, it is possible to restrain the occurrence of an accident.

The history of the abnormal traveling may be reflected by the evaluation and pay to the remote driver 1. Thereby, it is expected that the awareness of the remote driver 1 rises and the remote driver 1 performs the remote driving more carefully. This also contributes to the accident restraint.

6. Example of Remote Driving Taxi

6-1. Exemplary Configuration

FIG. 11 is a block diagram showing an exemplary configuration of the remote driving taxi 100 according to the embodiment. The remote driving taxi 100 includes a communication device 110, a sensor group 120, a traveling device 130, the display lamp 140, a control device 150, an outside-vehicle HMI 160, and an inside-vehicle HMI 170.

The communication device 110 communicates with the remote driving taxi management device 300.

The sensor group 120 includes a vehicle state sensor that detects the state of the remote driving taxi 100. The vehicle state sensor includes a speed sensor, an acceleration sensor, a yaw rate sensor, a steering angle sensor, and the like. Furthermore, the sensor group 120 includes a position sensor that detects the position of the remote driving taxi 100. Examples of the position sensor include a global positioning system (GPS) sensor. Furthermore, the sensor group 120 includes a recognition sensor that recognizes (detects) the situation in the periphery of the remote driving taxi 100. Examples of the recognition sensor include a camera, a laser imaging detection and ranging (LIDAR), and a radar.

The traveling device 130 includes a steering device 131, a driving device 132, and a braking device 133. The steering device 131 turns wheels. For example, the steering device 131 includes a power steering (electric power steering (EPS)) device. The driving device 132 is a dynamic power source that generates driving power. Examples of the driving device 132 include an engine, an electric motor, and an in-wheel motor. The braking device 133 generates braking power.

The display lamp 140 indicates whether the remote driving taxi 100 is currently available. Typically, the display lamp 140 is attached to the roof of the remote driving taxi 100.

The control device 150 controls the remote driving taxi 100. The control device 150 includes a single or a plurality of processors 151 (referred to as merely a processor 151 hereinafter), and a single or a plurality of storage devices 152 (referred to as merely a storage device 152 hereinafter). The processor 151 executes a variety of processes. For example, the processor 151 includes a central processing unit (CPU). The storage device 152 stores a variety of information necessary for the processing by the processor 151. Examples of the storage device 152 include a volatile memory, a nonvolatile memory, a hard disk drive (HDD), and a solid state drive (SSD). The control device 150 may include a single or a plurality of electronic control units (ECUs).

A vehicle control program PROG1 is a computer program that is executed by the processor 151. The vehicle control program PROG1 is stored in the storage device 152. Alternatively, the vehicle control program PROG1 may be recorded in a computer-readable recording medium. The processor 151 executes the vehicle control program PROG1, so that a function of the control device 150 is realized.

The outside-vehicle HMI 160 is attached to a side surface of the remote driving taxi 100. The user can convey an intention to use the remote driving taxi 100, by operating the outside-vehicle HMI 160. For example, the user presses a “use start button” that is displayed on the outside-vehicle HMI 160.

The inside-vehicle HMI 170 is installed in a cabin of the remote driving taxi 100. The inside-vehicle HMI 170 includes a display device, a speaker, a microphone, a touch panel, and the like. The user can convey the destination to the remote driver 1 using the inside-vehicle HMI 170. Further, the user can have a conversation with the remote driver 1 through the inside-vehicle HMI 170.

6-2. Information Acquisition Process, Communication Process

The processor 151 acquires driving environment information ENV indicating a driving environment of the remote driving taxi 100, using the sensor group 120. The driving environment information ENV is stored in the storage device 152. The driving environment information ENV includes vehicle position information, vehicle state information, and peripheral situation information. The vehicle position information indicates the position of the remote driving taxi 100 that is detected by the position sensor. The vehicle state information indicates a vehicle state that is detected by the vehicle state sensor.

The peripheral situation information indicates a recognition result by the recognition sensor. For example, the peripheral situation information includes an image that is picked up by the camera. The peripheral situation information may include physical body information relevant to a physical body in the periphery of the remote driving taxi 100. Examples of the physical body in the periphery of the remote driving taxi 100 include a pedestrian, another vehicle (a preceding vehicle, a parked vehicle, or the like), a sign, a white line, and a roadside structure. The physical body information indicates a relative position and relative speed of the physical body with respect to the remote driving taxi 100.

The vehicle information VCL is used in the remote driving of the remote driving taxi 100 by the remote driver 1. The vehicle information VCL includes at least some pieces of the above-described driving environment information ENV. For example, the vehicle information VCL includes the vehicle position information, the vehicle state information, and the peripheral situation information. Furthermore, the vehicle information VCL may include the current use state of the remote driving taxi 100. The vehicle management information 510 is updated based on the use state. Furthermore, the vehicle information VCL may include information that is input from the user through the outside-vehicle HMI 160 or the inside-vehicle HMI 170.

The processor 151 communicates with the remote driving taxi management device 300 through the communication device 110. For example, the processor 151 sends the vehicle information VCL to the remote driving taxi management device 300. As another example, the processor 151 sends the service request REQ_U to the remote driving taxi management device 300. Furthermore, as another example, the processor 151 receives the operation information OPE from the remote driving taxi management device 300. Furthermore, as another example, the processor 151 receives the instruction information INS from the remote driving taxi management device 300.

6-3. Vehicle Traveling Control

The processor 151 executes a vehicle traveling control for controlling the traveling of the remote driving taxi 100. The vehicle traveling control includes a steering control, a driving control, and a braking control. The processor 151 executes the vehicle traveling control by controlling the traveling device 130. More specifically, the processor 151 performs the steering control by controlling the steering device 131. The processor 151 performs the driving control by controlling the driving device 132. The processor 151 performs the braking control by controlling the braking device 133.

During the remote driving, the processor 151 performs the vehicle traveling control in accordance with the operation information OPE that is received from the remote driving taxi management device 300.

6-4. Display Lamp Control

In association with the display lamp control (see the above-described section 4), the processor 151 receives the instruction information INS for giving the instruction to put on or put off the display lamp 140, from the remote driving taxi management device 300. The processor 151 automatically puts on or puts off the display lamp 140 in accordance with the received instruction information INS.

6-5. Traveling Restriction Process

In association with the traveling restriction process (see the above-described section 5), the processor 151 receives the instruction information INS for giving the instruction of the traveling restriction, from the remote driving taxi management device 300. The processor 151 performs the traveling restriction in accordance with the received instruction information INS.

Alternatively, the processor 151 may determine whether there is the abnormal traveling of the own vehicle, based on the vehicle information VCL. In the case where the abnormal traveling is detected, the processor 151 performs the traveling restriction.

7. Example of Remote Driver Terminal

7-1. Exemplary Configuration

FIG. 12 is a block diagram showing an exemplary configuration of the remote driver terminal 200 according to the embodiment. The remote driver terminal 200 includes a communication device 210, a display device 220, a remote operation member 230, a driver monitor 240, and a control device 250.

The communication device 210 communicates with the remote driving taxi management device 300.

The display device 220 presents a variety of information to the remote driver 1 by displaying the variety of information.

The remote operation member 230 is a member that is operated by the remote driver 1 at the time of the remote driving (remote operation) of the remote driving taxi 100. The remote operation member 230 includes a steering wheel 231, an accelerator pedal 232, a brake pedal 233, a direction indicator, and the like.

The driver monitor 240 detects the biological information (heart rate, pulse, eye movement, and the like) about the remote driver 1.

The control device 250 controls the remote driver terminal 200. The control device 250 includes a single or a plurality of processors 251 (referred to as merely a processor 251 hereinafter), and a single or a plurality of storage devices 252 (referred to as merely a storage device 252 hereinafter). The processor 251 executes a variety of processes. For example, the processor 251 includes a CPU. The storage device 252 stores a variety of information necessary for the processing by the processor 251. Examples of the storage device 252 include a volatile memory, a nonvolatile memory, an HDD, and as SSD.

A remote driving program PROG2 is a computer program that is executed by the processor 251. The remote driving program PROG2 is stored in the storage device 252. Alternatively, the remote driving program PROG2 may be recorded in a computer-readable recording medium. The remote driving program PROG2 may be provided via a network. The processor 251 executes the remote driving program PROG2, so that a function of the control device 250 is realized.

7-2. Remote Driving Process

The processor 251 communicates with the remote driving taxi management device 300 through the communication device 210. The processor 251 receives the vehicle information VCL sent from the remote driving taxi 100 to which the remote driver 1 has been assigned. The vehicle information VCL is stored in the storage device 252. The processor 251 presents the vehicle information VCL to the remote driver 1 by displaying the vehicle information VCL on the display device 220. Further, the processor 251 displays the map information on the display device 220. The remote driver 1 can know the situation of the remote driving taxi 100, based on the map information and vehicle information VCL displayed on the display device 220.

The remote driver 1 operates the remote operation member 230. The processor 251 acquires the operation amount of the remote operation member 230 by the remote driver 1. The operation amount is detected by a sensor that is installed in the remote operation member 230. The processor 251 generates the operation information OPE that reflects the operation amount, and sends the operation information OPE to the remote driving taxi management device 300.

7-3. Assignment Process

In association with the assignment process (see the above-described section 3-2), the processor 251 sends the assignment request REQ_D input by the remote driver 1, to the remote driving taxi management device 300. Further, the processor 251 receives the assignment notice ASN from the remote driving taxi management device 300.

7-4. Information Notification Process

The processor 251 may give notice of the current driver state to the remote driving taxi management device 300 through the communication device 210. The driver management information 520 is updated based on the driver state.

7-5. Traveling Restriction Process

In association with the traveling restriction process (see the above-described section 5), the processor 251 determines whether there is the abnormality of the remote driver 1, based on the detection result by the driver monitor 240. In the case where the abnormality of the remote driver 1 is detected, the processor 251 gives notice of the occurrence of the driver abnormality to the remote driving taxi management device 300. Alternatively, the processor 251 may send the biological information detected by the driver monitor, to the remote driving taxi management device 300.

8. Example of Remote Driving Taxi Management Device

8-1. Exemplary Configuration

FIG. 13 is a block diagram showing an exemplary configuration of the remote driving taxi management device 300 according to the embodiment. The remote driving taxi management device 300 includes a communication device 310 and a control device 350.

The communication device 310 communicates with each of the remote driving taxi 100, the remote driver terminal 200, and the user terminal 400.

The control device 350 controls the remote driving taxi management device 300. The control device 350 includes a single or a plurality of processors 351 (referred to as merely a processor 351 hereinafter), and a single or a plurality of storage devices 352 (referred to as merely a storage device 352 hereinafter). The processor 351 executes a variety of processes. For example, the processor 351 includes a CPU. The storage device 352 stores a variety of information necessary for the processing by the processor 351. For example, the management information 500 (see FIG. 3 ) is stored in the storage device 352. Examples of the storage device 352 include a volatile memory, a nonvolatile memory, an HDD, and an SSD.

A management program PROG3 is a computer program that is executed by the processor 351. The management program PROG3 is stored in the storage device 352. Alternatively, the management program PROG3 may be recorded in a computer-readable recording medium. The management program PROG3 may be provided via a network. The processor 351 executes the management program PROG3, so that a function of the control device 350 is realized.

8-2. Remote Driving Process

The processor 351 communicates with the remote driving taxi 100 and the remote driver terminal 200 through the communication device 310. The processor 351 receives the vehicle information VCL from the remote driving taxi 100, and transfers the vehicle information VCL to the remote driver terminal 200. Further, the processor 351 receives the operation information OPE from the remote driver terminal 200, and transfers the operation information OPE to the remote driving taxi 100.

8-3. Assignment Process

In association with the assignment process (see the above-described section 3), the processor 351 receives the assignment request REQ_D from the remote driver terminal 200. Further, the processor 351 receives the service request REQ_U from the remote driving taxi 100 or the user terminal 400. In response to the assignment request REQ_D or the service request REQ_U, the processor 351 executes the assignment process based on the management information 500 (see the above-described sections 3-2, 3-3). The processor 351 updates the management information 500 based on a result of the assignment process. Further, the processor 351 sends the assignment notice ASN to the remote driver terminal 200. Further, the processor 351 sends the service information INF to the user terminal 400.

8-4. Display Lamp Control

In association with the display lamp control (see the above-described section 4), the processor 351 recognizes the user state of each remote driving taxi 100, and the like, based on the management information 500, and determines the putting-on or putting-off of the display lamp 140. Then, the processor 351 sends the instruction information INS for giving the instruction to put on or put off the display lamp 140, to the remote driving taxi 100.

8-5. Traveling Restriction Process

In association with the traveling restriction process (see the above-described section 5), the processor 351 acquires the vehicle information VCL from the remote driving taxi 100 that is being driven by the remote driver 1. The processor 351 monitors the traveling state of the remote driving taxi 100 based on the vehicle information VCL, and determines whether there is the abnormal traveling. The processor 351 sends the instruction information INS for giving the instruction of the traveling restriction, to the remote driving taxi 100 that is performing the abnormal traveling.

Further, the processor 351 receives the notice of the occurrence of the driver abnormality, from the remote driver terminal 200. The processor 351 sends the instruction information INS for giving the instruction of the traveling restriction, to the remote driving taxi 100 that is being driven by the remote driver 1 in which the abnormality has occurred.

9. Demand Prediction

It is useful to predict the demand for the remote driving taxi service for each area. For example, based on the demand prediction, it is possible to optimize the disposition of the remote driving taxi 100 for each area. For example, it is possible to previously dispose a greater number of remote driving taxis 100 to an area where the demand is high. Thereby, the service opportunity increases, and the profit increases. Further, the waiting time of the user is shortened, and therefore the user satisfaction level is enhanced. 

What is claimed is:
 1. A remote driving taxi system that provides a mobility service, the mobility service using remote driving taxis that are driven by remote drivers, the remote driving taxi system comprising: a single or a plurality of processors; and a single or a plurality of storage devices configured to store management information including assignment states between the remote driving taxis and the remote drivers, wherein: the single or the plurality of processors executes an assignment process based on the management information, in response to a request from a user; and in the assignment process, the single or the plurality of processors selects one of unassigned taxis as a first remote driving taxi that provides the mobility service to the user, each of the unassigned taxis being the remote driving taxi to which the remote driver has not been assigned, selects one of unassigned drivers as a first remote driver that provides the mobility service to the user, each of the unassigned drivers being the remote driver that has not been assigned to the remote driving taxi, and assigns the first remote driver to the first remote taxi.
 2. The remote driving taxi system according to claim 1, wherein: the management information further includes driver property information indicating properties of the remote drivers; and the single or the plurality of processors selects the first remote driver based on the driver property information.
 3. The remote driving taxi system according to claim 2, wherein: the management information further includes current positions of the remote driving taxis; the driver property information includes desired areas of the remote drivers; and the single or the plurality of processors selects the unassigned driver for which the desired area contains the current position of the first remote driving taxi, as the first remote driver.
 4. The remote driving taxi system according to claim 2, wherein: the management information further includes vehicle types of the remote driving taxis; the driver property information includes desired vehicle types of the remote drivers; and the single or the plurality of processors selects the unassigned driver for which the desired vehicle type coincides with the vehicle type of the first remote driving taxi, as the first remote driver.
 5. The remote driving taxi system according to claim 2, wherein: the driver property information includes ranks of the remote drivers; the request from the user includes a desired rank that is desired by the user; and the single or the plurality of processors selects the unassigned driver for which the rank is equal to or higher than the desired rank, as the first remote driver.
 6. The remote driving taxi system according to claim 1, wherein: the management information further includes a waiting list indicating a priority order of the unassigned driver relevant to the assignment process; and the single or the plurality of processors selects the first remote driver in accordance with the priority order indicated in the waiting list.
 7. The remote driving taxi system according to claim 1, wherein: the request from the user includes a desired getting-in position; the management information further includes current positions of the remote driving taxis; and the single or the plurality of processors selects the unassigned taxi that exists within a predetermined range from the desired getting-in position, as the first remote driving taxi.
 8. A mobility service management method for managing a mobility service, the mobility service using remote driving taxis that are driven by remote drivers, the mobility service management method comprising: a process of acquiring management information including assignment states between the remote driving taxis and the remote drivers; and a process of executing an assignment process based on the management information, in response to a request from a user, wherein the assignment process includes: a process of selecting one of unassigned taxis as a first remote driving taxi that provides the mobility service to the user, each of the unassigned taxis being the remote driving taxi to which the remote driver has not been assigned; a process of selecting one of unassigned drivers as a first remote driver that provides the mobility service to the user, each of the unassigned drivers being the remote driver that has not been assigned to the remote driving taxi; and a process of assigning the first remote driver to the first remote taxi.
 9. A remote driving taxi management device that manages a mobility service, the mobility service using remote driving taxis that are driven by remote drivers, the remote driving taxi management device comprising: a single or a plurality of processors; and a single or a plurality of storage devices configured to store management information including assignment states between the remote driving taxis and the remote drivers, wherein: the single or the plurality of processors executes an assignment process based on the management information, in response to a request from a user; and in the assignment process, the single or the plurality of processors selects one of unassigned taxis as a first remote driving taxi that provides the mobility service to the user, each of the unassigned taxis being the remote driving taxi to which the remote driver has not been assigned, selects one of unassigned drivers as a first remote driver that provides the mobility service to the user, each of the unassigned drivers being the remote driver that has not been assigned to the remote driving taxi, and assigns the first remote driver to the first remote taxi. 